"Accumulator Scan"

"Accumulator Setup"

"Analog Input Configuration"

"Analog Input Control"

"Analog IO Status"

The "Configurable Data Group" data group provides a flexible way to create custom data groups on a per-device basis. See Configurable Data Group.

Four "Command Message (Configurable)" data groups exist by default:

• Turn Well On (524)
• Force Well Into Idle Time (525)
• Clear Errors (523)
• Force Off Until Reset (31)

Additional "Command Message (Configurable)" data groups can be added.

If you choose to add a "Command Message (Configurable)" data group, its parameter number must correspond to the appropriate number exposed in the dgElements section of the CmdCfgMsg data group in the device template file.

Four corresponding default UIS commands preexist for the four default "Command Message (Configurable)" data groups.

In the remote device editor, click View Data for this data group, click Edit, then double-click in the parmIdTxt New Value field to generate a drop-down menu of available commands.

The "Command Message" data group enables a user to send one of four commands to a field device:

• Turn Well On
• Force Well Into Idle Time
• Clear Errors
• Force Off Until Reset

"Counter Balance Effect"

The "Composite Data Group" is a special kind of data group that enables you to combine any data group element(s) from any data group(s) as long as they are in the same template as the composite data group.

The "Composite Data Group" does not appear in a remote device editor unless it has been defined in the relevant device template file.

See Composite Data Group.

"Comm Setup"

For the "Controller Version Information" data group, the following conditions describe when relevant function codes are used:

• If FWPNum is FW-00004-00, FC25 is used.
• If FWPNum is not FW-00004-00 and the FWVersID is less than 3, FC16 is used.
• If FWPNum is not FW-00004-00 and the FWVersID is greater than or equal to 3, FC16 Ext is used.

"Control Parameters"

"Control Timers"

The "Cycle Run Time History" data group retrieves and stores data for the current runtime cycle and the previous 17 runtime cycles.

Values displayed are in total number of seconds and equivalent hh:mm:ss format.

"Cycle Run Time History (0-59)"

"Cycle Run Time History (60-119)"

"Date and Time" You can sync the field device time to the host time by clicking Set to host time in the remote device editor.

"Downhole Calculation Results"

"Downhole Setup"

"Digital Input Counters"

"Daily Elapsed Run Times, 120 day"

The "Daily Fluid Production – 30 Day" data group collects and displays fluid production (in BBL) for the 30 days prior to the current day. Data is displayed in table and corresponding graph format.

The "Daily Fluid Production – 120 Day" data group collects and displays fluid production (in BBL) for the 120 days prior to the current day. Data is displayed in table and corresponding graph format.

The "Daily Percent Run Times – 8 day" data group collects and displays the percentage of a calendar day that the associated well was operating for the 8 days prior to the current day. Data is displayed in table and graph format.

The current day's data displays only a partial day's data since the day is not yet complete.

The "Daily Percent Run Times – 30 Day" data group collects and displays the percentage of a calendar day that the associated well was operating for the 30 days prior to the current day. Data is displayed in table and graph format.

The current day's data displays only a partial day's data since the day is not yet complete.

The "Daily Percent Run Times – 120 Day" data group collects and displays the percentage of a calendar day that the associated well was operating for the 120 days prior to the current day. Data is displayed in table and graph format.

The current day's data displays only a partial day's data since the day is not yet complete.

The "Downhole Configuration" data group enables you to manually enter downhole configuration settings into the host-side remote device for accurate host calculations.

This data group neither reads data from nor sends data to an associated field device.

This data group is required if you want to generate downhole cards and/or if you are connecting this device to the CygNet Dynagraph Viewer client application.

Click Edit to overwrite existing values.

Click Edit then click Add to add rod segment configuration details to the Rod Segment Definition dialog box. The Select Rod Category and Type drop-down menu populates the Rod Type field.

The "Dynagraph Card" data group retrieves and displays surface and/or downhole rod pump cycle data. Data is displayed in table and graph format.

Depending on your device model, you must retrieve one or more of these data groups before retrieving dynagraph cards: "Controller Version Information," "Pumpoff Configuration," "Stroke Length," and/or "Stroke Length Settings."

These "Dynagraph Card" data groups exist by default:

• Current Card — A current card describes the most recent stroke stored in the RTU. This card type is used for analyzing real-time pump information.
• Shutdown Card — A shutdown card, or pump-off card, is generated when the pump is turned off, usually to wait for the reservoir to fill.
• Pumpup Card — A pumpup card is generated when the pump starts again after having been shut down.
• Reference Card — A quick reference or snapshot of a dynagraph card. Results from clicking the Save Reference button.
• Ideal Card — Returned from an external system. Calculates an ideal rod pump cycle card based on a set of configuration items. Can be used as a way to compare actual and ideal cycles, and to adjust current configuration to a more ideal state.
• Alarm Card — An alarm card is created whenever an alarm condition is met in a field device. Such a condition is typically treated as less severe than a fault, which creates a failure card.
• Failure Card — A failure card is created whenever a fault condition is met in a field device. Such a condition is typically treated as more severe than an alarm, which creates an alarm card.

This data group is required if you are connecting this device to the CygNet Dynagraph Viewer client application.

This data group can display up to 5 cards per card type.

Downhole card functionality is only available if your device uses firmware that supports function code 25 (FC25). FC25 is used to retrieve downhole dynagraph card data if the associated field device firmware version ID is at least 1.01.02 and the firmware part number is FW-00004-00. Firmware information is retrieved using the Controller Version Information (CtrlInfo) data group.

Ordinals associated with the different data group types are hard coded. For instance, ordinal 0 is always Current Card, ordinal 1 is always Shutdown Card, and so forth. Ordinals here do not merely identify a sequence of "Dynagraph Card" data groups.

Click Details for table-format plot data and other details.

Click Save Reference to save a reference card to the default "Dynagraph Card" data group that uses the data group description Reference Card.

This data group references a specific subset of support data groups and elements. These items are required to support a connected system; they are not required if you are not reliant on a connected system for functionality or data.

The "Pumpoff Configuration" data group defines allowable limits used in dynagraph card display and alarming.

Limits include those used to create a pump-off setpoint, including the number of allowable strokes before action must be taken, and peak and minimum load limits, including the number of allowable strokes before action must be taken.

Finally, you can choose from several pump-off control methods. The method you choose is reflected in your dynagraph cards.

If Min Load (pounds) is set to 0, low load violations are not detected. If Peak Load (pounds) is set to 0, peak load violations are not detected.

A red dashed line appears on the dynagraph card to indicate min and peak load limits as defined for this data group.

In the Peak/Min Load section, Consecutive Strokes is the acceptable number of consecutive times a load violation (peak or min) is allowed before action must be taken. If set to 0, all load violation limits are disabled.

In the Pump-Off Control Setpoint section, Consecutive Strokes is the acceptable number of consecutive strokes that can occur before action must be taken. A value of 1 entered for this field might be too few strokes to reliably indicate that pumpoff is occurring.

This data group is required if you want to generate shutdown/pumpoff cards and/or if you are connecting this device to the CygNet Dynagraph Viewer client application.

The "DynaCard Support" data group is used to calculate a timestamp for pumpup cards or shutdown cards if used in conjunction with an older field device and an external system. Otherwise, it is unneeded.

If the WellState is running (current value of 1 or 2), a timestamp is calculated in one of the two following ways:

• Pumpup Timestamp = (TmLstCtrlC + DtLstCtrlC) - LastPOTm
• Shutdown Timestamp = TmLstCtrlC + DtLstCtrlC

If the WellState is not running (any current value other than 1 or 2), a timestamp is calculated in one of the two following ways:

• Pumpup Timestamp = (TmLstCtrlC + DtLstCtrlC) - LstRnTmI
• Shutdown Timestamp = TmLstCtrlC + DtLstCtrlC

This data group is chained in if it is required. Otherwise, it is unaffected. You can manually add one to your Data Groups list for display or troubleshooting purposes, but this is not necessary in order to take advantage of its functionality.

An "Event Directory" data group poll requests all types of events. On the View Data dialog box of the "Event Directory" data group, from the Options drop-down menu, select Get selected event cards to read the cards associated with the highlighted event.

A user-defined UIS command can allow you to specify any combination of plain, alarm, and fault events.

Event types are:

• Plain: Any event that is not an alarm or fault event. Can be thought of as normal.
• Alarm: Occurs when an alarm flag is set in the controller.
• Fault: Indicates an exception, malfunction, or other process failure. It is the most severe event type.

If you have already implemented eProdRPC templates that do not have the "Event Directory" data group XML, you must manually add the "Event Directory" data group XML and reload the new device definition (device template file) to the Device Definition Service (DDS). It is safest to use the CygNet Device Template Manager utility to do so.

"Flow Control Unit Date Time"

"Flow Computer Unit Pressure"

"Flow Computer Unit Flow Status"

"Flow Computer Unit Setup"

"Gross Fluid Calculation Settings"

"Gross Fluid Calculation Settings"

"Load Values Summary"

"Load Violations Setup"

"Logger Freeze Buffer, Daily"

"Logger Freeze Buffer, Hourly"

"Logger Setup"

"Peak Energy Mgmt Config"

"Power Failure Data"

"Rod Types"

"Sensor Setup"

"Single Parameter" Refer to eProdRPC documentation for a complete list of parameters. See eProdRPC Single-Parameter Data Group.

The "Status Data" data group is a useful resource if you are using the CygNet Dynagraph Viewer client application. Use it as a catalog of data group elements that can map to UDCs and/or the CygNet Dynagraph Viewer.

The "Stroke Length" data group writes a manually entered stroke length to the host-side remote device for various calculations. This value is not written to the actual field device.

Card position is typically returned as a % of stroke length between top of shaft and bottom of shaft. To report the position in distance, not %, stroke length is required.

The EProdRpc_8500.dtf requires you to use the "Stroke Length" data group to manually set the stroke length for devices.

The "Stroke Length Settings" data group retrieves the stroke length configured on the field device. Stroke length on the field device can be overwritten using this data group.

Card position is typically returned as a % of stroke length between top of shaft and bottom of shaft. To report the position in distance, not %, stroke length is required.

The EProdRpc_8800v204Legacy.dtf requires you to use the "Stroke Length Settings" data group to manually set the stroke length for devices.

"Tank Level Status"

"Task Failure Data"

"Tank Level Setup"

The "Valve Check Data" data group enables the retrieval of valve load values for both standing and traveling valves. It is available for use with the WellPilotRPOC device type.

You must poll VlvChkInfo before polling ValveCheck.

You must poll VlvChkInfo before polling ValveCheck.

"Valve Check Support Info"

"Yaskawa VSD Configuration"

"Yaskawa VSD Control Status"

"Yaskawa VSD Operation History"

"Yaskawa VSD Rod Load Ctrl Hist

"VSD Rod Load Control Setup"

"Yaskawa VSD Setup"

"Yaskawa VSD Status"